home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
gt_power
/
bguti23.zip
/
BGUTI.DOC
next >
Wrap
Text File
|
1990-05-20
|
14KB
|
255 lines
VOICE B.J. GUILLOT MODEM
(713) 893-9123 2611 RUSHWOOD CIRCLE (713) 893-9124
HOUSTON, TX 77067-1941
Copyright B.J. Guillot 1989-90, All Rights Reserved.
--------------------------------------------------------------
BGUTI 2.2 20 MAY 90
--------------------------------------------------------------
GT POWER 15.XX UNIVERSAL TEXT INTERFACE DRIVER
FOR RELAYNET AND MEGAMAIL DOOR INTERFACING
--------------------------------------------------------------
ABSTRACT
--------------------------------------------------------------
This UTI corresponds with Kip Compton's Revision 2 Standards.
As a result, you now not only have the option of joining any
PC Relay Network, but you can use the new mail door, MegaDoor,
on your system to allow your users to download mail packets
and read new mail on their own system giving your system more
time for callers to come in. It allows your users to read
the messages on their own time, at their own pace. Since
MegaDoor uses UTI drivers, the MegaDoor/MegaRead combo can be
used on any BBS system, so your users will not have to learn
all of GT Power's commands besides how to open a door.
--------------------------------------------------------------
ODDITIES
--------------------------------------------------------------
Any mention of "RelayNet" in this documentation also means
RelayNet International Message Exchange (RIME), Intelec,
QuickLink, or any existing network using Kip Compton's
PC Relay Networking Software.
If you are already an GT Network Sysop, you may find RelayNet
strange in some aspects. For example, you use a SCRIPT to
call your RelayNet HUB at a TIME CONVIENIENT FOR BOTH OF YOU.
You, as a RelayNet Node, are unable to call any other node on
the RelayNet Network. You ONLY call your HUB to get echomail
conferences, i.e., there is no Mail Driver program. You will
be REQUIRED to carry the RelayNet "Common" Echomail
conference, which is carried by ALL RelayNet Nodes, Hubs, etc.
An interesting feature of RelayNet and this driver is that it
gives you complete echomail "threading" abilities, i.e., you
can be directed to the original message, (also see syntax).
--------------------------------------------------------------
INCLUDED FILES
--------------------------------------------------------------
BGUTI.DOC - This File, Main Documentation .........
BGUTI.NEW - New Information .......................
MEGADOOR.BAT - Sample Batch File for MegaDoor ........
RELAY.BAT - Sample Batch File for RelayNet 0.9ß12A
RELAY.SCR - Sample Script for Calling Hub .........
RELAY1.SCR - Sample Fancy Script by Jim Kreyling ...
UTIDOOR.EXE - Sends MegaDoor the Baud Rate, Etc. ....
UTIHIGH.EXE - Finds Highest Message Number ..........
UTIEXPRT.EXE - Bags Mail from GT into UTI Format .....
UTIIMPRT.EXE - Distributes Mail from UTI Format to GT.
UTILIST.EXE - Sends MegaDoor GT Message Area Data ...
UTILSTRD.EXE - Reads/Update User Last Read Pointers ..
UTIVER.EXE - Displays UTI Revison Number and ID ....
I, for one, hate having multiple EXE files, but you need to
remember, I am programming for a "standard", and cannot change
the way things work.
You do not need any of the GT Network files: NODELIST.BBS,
ROUTING.BBS, MBAGxxx.COM, MDRIVxxx.COM, or MDISTxxx.COM unless
you are also running with the GT Network.
--------------------------------------------------------------
REQUIRED FILES -- MEGADOOR
--------------------------------------------------------------
In order for your users to use MegaDoor, they will need to
first download the MegaReader program. Currently MREAD10.ZIP.
Copy all the UTI*.EXE files into your MegaDoor directory. If
you are also planning on running RelayNet, ... I would put
the UTI*.EXE files and MegaDoor files in your PC Relay
directory to save space.
GTUSER.BBS, GTMDIR.BBS, and USER.CTL must all reside in your
GTPATH directory. MESSAGE.CTL and USER_MSG.CTL files are also
accessed by MegaDoor depending on what conferences the user
is joined in.
The user can only send/receive mail from conferences that he
or she is joined in. The user has control from their system
to set the last read pointers of GT to whatever they specify
They may remove a message area by using the UN)Join command
off the main menu, or join a message area by using the A)rea
Change command off the main menu.
--------------------------------------------------------------
REQUIRED FILES -- RELAYNET
--------------------------------------------------------------
In order for you to become a RelayNet Node, you will HAVE TO
register the RelayNet Node Software, currently thrity dollars.
Please consult your RelayNet Hub for help in setting up the
basic parts. (A discount is availble for registered users of
any networking software, including GT, (see PCRELAY.TXT)).
You will not be able to run the CONFIG.EXE program until your
hub fetches your ID files for you. This process usually takes
around fourty-eight hours.
Make sure, when your Hub tells you to run CONFIG.EXE, that you
select the option called "UTI Driver Revision 2" under system
type and not "PC Board", "RBBS", or "UTI Driver".
As per the request of the RelayNet manual, I am supposed to
tell you what your conference ID's are. For this driver, they
will be the paths of the GT message bases, as specified
in your GTMDIR.BBS file. For example, if you have this in
your GTMDIR.BBS...
W ^D:\MAIL\RNET004 RelayNet Common Conference
...your Conference ID for the "Common" Conference would be
"D:\MAIL\RNET004" (without the quotes).
If you don't understand the basic setup of RelayNet, please
consult your Local RelayNet Hub system or me for further
details.
--------------------------------------------------------------
HOW TO RUN BGUTI -- RELAYNET
--------------------------------------------------------------
Make sure you have the UTI*.EXE programs in the same directory
with all your RelayNet programs, as well as the RELAY.SCR file
in your Script Directory, (as specified by GT Power).
You, yourself, never need to run the UTI*.EXE files. They are
shelled to by EXP.EXE and IMP.EXE, and my programs are mainly
transparent. All high number storage and tracking are kept
up transparently also. All you need to do is sit back and
relax. Again, the UTI driver is run transparently by PCRelay.
You use PCRelay's CONFIG.EXE to add/delete conferences as you
need to. BGUTI is capable of "auto-priming". After doing
this, BGUTI will promt your for an "access level" and
"description" for the conference and will automatically append
it to your GTMDIR.BBS file.
Messages sent to PCRelay will me marked as <MAILED> on your
system to help you discover if the software is working right,
and messages imported from PCRelay will be marked as <NO KILL>
To use "bridge" mode (in which the rcvd/mailed flag is not
messed with at all), simply prefix the message directory
pathname with a "$" via the CONFIG.EXE program. Messages
exported in "bridged" mode have their "Route:" lines stripped,
and there origin lines are stripped to one line. The phrase
".ORIGIN:" is changed to "* AfsNet:".
--------------------------------------------------------------
TROUBLE SHOOTING -- MEGADOOR
--------------------------------------------------------------
Q) When I try to run the door locally, MegaDoor tells me that
there is no such thing as COM Port 0.
A) A seperate batch file is required for running MegaDoor
locally. Check out the LOCAL.BAT file included with
MDOOR10.ZIP.
Q) UTIDOOR.EXE is not reporting the correct DTE Baud Rate.
A) If you are running a version of GT prior to 15.10 Beta #11,
users with different DTE/DCE Baudrates will not be able to
use MegaDoor. Sorry, but there is nothing I can do to fix
this.
Q) Users with one named handles cannot use MegaDoor.
A) If you are running a version of GT prior to 15.10 Beta #11,
users with one named handles cannot use MegaDoor.
Since MegaDoor and MegaRead are not my products, there is not
much else I can help you with. You will need to get in touch
with Kip Compton for additional help if you are positive the
UTI driver is not causing the problem.
--------------------------------------------------------------
TROUBLE SHOOTING -- RELAYNET
--------------------------------------------------------------
Some of this material may be duplicated, but after all, this
may be the only part of the documentation some people read.
Q) When I run CONFIG, it immediately quits to DOS saying it's
missing the ID file.
A) You first have to contact your hub or regional hub and tell
them you need to get an ID file to join the network. They
will tell you what other information they need.
Q) When I attempt to add a conference with CONFIG, it asks me
for an "ID:".
A) The "ID:" will be the message area pathname of the echo.
It should be identical to what's listed in your GTMDIR.BBS.
Q) When the UTI programs are shelled to, they come up with
numerous RUNTIME ERRORS and FILE NOT FOUNDS.
A) Did you run CONFIG.EXE to add and "auto-prime" the
conferences?
Q) How do people send private echomail messages to my system,
and are they intercepted at any other node?
A) Private messages can only be intercepted by the Sysop of
the board the user is on. To receieve private messages,
you must create a private mailbox using the CONFIG.EXE
program or sending a special message to the network. See
the document files that come with PCRelay for more info.
--------------------------------------------------------------
OTHER INFORMATION
--------------------------------------------------------------
I would suggest to use Sysop's Tools or JDCTL.EXE to delete
messages rather than using the OZ DELMSG.EXE program. It does
not kill deleted headers and makes the UTI functions much
slower. I would also suggest not to renumber the messages, as
that could cause some problems with the UTI driver knowing
what messages have already been exported. If, however, you
still wish to renumber messages, you MUST run RESET.EXE AFTER
running the renumbering problem, and you MUST delete the
THREAD.xxx files in your PC Relay directory.
This program was made with Turbo Pascal 5.5 on a Tandy 1000 SX
computer. This program is not LAN specific. Source code will
be availble only to Registered GT Developers. You may modify
the source code in any way you need to, but you are not
allowed the distribute the changed programs and/or source code
to any other user of this program, (as by the GT Developer
Toolkit Contract).
All EXE files have been compressed with LZEXE 0.91.
If you have any suggestions or comments please address them
to me via "Sysops" or "Admin" confernces in RelayNet, or the
original GT companions conference or at AFS Net/Node 440/003.
No registration of this program is required, yet I recommend
you register GT Power 15/MegaRead if you have not already.
Regards, Relay TRANQUIL
B.J. Guillot (713) 893-9124